Description

New template for Ivy's Studio Website service. Adds the DNS records needed to point an operator's custom domain at their Ivy's Studio website (a marketing site for short-term rental accommodations).

Type of change

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

• Template functionality checked using Online Editor
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

• syncPubKeyDomain is set (dcsig.studio.ivy-s.de)
• warnPhishing is not set alongside syncPubKeyDomain
• syncRedirectDomain is set (studio.ivy-s.de) — the service's apply flow uses redirect_uri to return to the operator's session in our app after the registrar writes records
• no TXT record contains SPF content (template has no TXT records)
• txtConflictMatchingMode — not applicable (no TXT records)
• no variable is used as a bare full record value, EXCEPT the A record's pointsTo: "%IP%". Justification: an A record's value is a literal IP address by definition; there is no non-bare formulation. Same pattern as accepted templates like treadcommand.com.custom-domain.json (pointsTo: "%target%").
• no bare variable is used as the full host label (all hosts are literals: @ and www)
• no variable is used in the host field to create a subdomain
• %host% does not appear in any host attribute
• essential is intentionally not set on either record — both are required for the service to function (removing either breaks the website serving)

Online Editor test results

Editor test link(s):

• Apex attach (example.com, no host): Test studio.ivy-s.de/custom-domain example.com/@
• Subdomain attach (example.com, host=blog): Test studio.ivy-s.de/custom-domain example.com/blog